feat: format-module-bytes utility
#1236
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
l-monninger
reviewed
May 21, 2025
andygolay
changed the title
format-module-bytes utility
l-monninger
approved these changes
May 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
format-module-bytesutility to provide the serialized args for callingcode::publish_package_txnon Movement explorer.Changelog
format-module-bytesand tests.Usage
See the README for instructions with the included example
hello.movepackage.The main steps are:
util/format-module-bytes,movement initor copy in a.movement/config.yamlinto theutil/format-module-bytesdir to set up the account you intend to use for publishing. Thedefaultprofile is the one used in this util.sources.cargo run -p format-module-bytes.movement/config.yaml. (Ensure the account is funded.)Testing
Unit tests:
cargo test -p format-module-bytesE2E testing is best done manually; you should be able to publish the package with the serialized inputs and see a success result as follows:
